Matrix Tree Presentation Structures

ABSTRACT

Approaches for rendering data on a display are provided using matrix tree and matrix tree table presentation structures. A matrix table is rendered on a display. The matrix table comprises a set of columns and a set of rows. Each column is associated with a different dimension instance of a first dimension, and each row is associated with a different dimension instance of a second dimension. The intersection of each column and row is a cell. In one approach, a tree of nodes is rendered within at least one cell of the matrix table. In another approach, a tree table is rendered within at least one cell of the matrix table. The tree table comprises a tree of nodes, where each node of the tree of nodes comprises a row of data. A tree of nodes in a cell of the matrix table may be expanded or collapsed upon request.

RELATED APPLICATION DATA

This application is related to U.S. Pat. No. ______ (Attorney Docket Number ORC_(—)1002), entitled “Nested Dimensions Presentation Structures,” filed concurrently herewith, invented by Akhil Choudhury, the contents of which are herein incorporated by reference for all purposes as if fully set forth herein.

FIELD OF THE INVENTION

Embodiments of the present invention relate to rendering data on a display.

BACKGROUND OF THE INVENTION

There are many contexts in which a computerized entity may need to retrieve, arrange, and display data to a user in a manner that facilities understanding of the data. For example, computerized entities are often responsible for constructing web pages or other visual presentations that are rendered on a display device. Such web pages and visual presentations often employ a presentation structure that organizes the data and depicts relationships lying therein. A presentation structure, as used herein, is a structured format for depicting data on a display.

One such presentation structure is a tree. A tree is an acyclic connected graph where each node has a set of zero or more child nodes and at most one parent node. A tree may be helpful for organizing or classifying data as every node in the tree can be traced to a single origin through a unique path.

According to one approach for using a tree, data is initially retrieved from a database by an application server that issues a database command (a “select statement”) to a database server. The database server processes the database command, retrieves the data from the database, and provides the data to the application server. The application server then assembles the data in a tree structure that forms part of a web page. The application server sends the web page to a web server. The web server sends the web page to a web browser, which in turn renders the web page on a display. The viewer of the web page can more readily digest the organization and structure of the data by its depiction in the tree.

A problem with trees is that they do not allow the data stored therein to be easily analyzed across multiple dimensions. To illustrate, assume a particular tree stores employee data in each node of the tree. If a user wishes to view employee data for a desired region, then employee data for the desired region will need to be retrieved so the tree may be populated with the appropriate data. The employee data for the desired region can be obtained by issuing a select statement, to the database server, that identifies the desired region as a filter value in a “where clause.” Thereafter, if the user wishes to view employee data for new region, then another select statement with a filter value identifying the new region will need to be executed, and the tree once again will need to be populated with the newly retrieved data. Executing multiple database commands in this manner is not desirable, as it increases the computational resources as well as the time and effort involved in viewing the necessary data.

The other presentation structures that are currently available, such as a table, also have disadvantages which limit their usefulness for analyzing data across multiple dimensions. Therefore, improved approaches for presenting data to a user would be desirable. The approaches described in this section are approaches that could be pursued, but not necessarily approaches that have been previously conceived or pursued. Therefore, unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section.

SUMMARY OF THE INVENTION

Improved techniques are provided for rendering data on a display. Embodiments of the invention advantageously depict data using a new presentation structure that presents hierarchical data and relational data in a unified manner. Advantageously, embodiments of the invention enable a user to view data from perspectives not previously possible without repopulating the presentation structure used to display the data.

In an embodiment, a presentation manager retrieves data from a storage medium. The presentation manager instructs a display manager to render a visual presentation depicting the retrieved data on a display device. The visual presentation includes a matrix table. The matrix table comprises a set of columns and a set of rows. Each column is associated with a different dimension instance of a first dimension, and each row is associated with a different dimension instance of a second dimension. The intersection of each column and row of the matrix table is referred to as a cell.

In one approach, a tree of nodes is rendered within at least one cell of the matrix table. In another approach, a tree table is rendered within at least one cell of the matrix table. A tree table comprises a tree of nodes, where each node of the tree of nodes comprises a row of data. A tree of nodes in a cell of the matrix table may be expanded or collapsed upon request.

Advantageously, embodiments of the invention may (a) render hierarchical data in a tree table or tree of each node of a matrix table while (b) rendering relational data in the rows and columns of the matrix table. Embodiments of the invention enable one to view multiple sets of hierarchical data simultaneously, thereby saving time and computational resources. In addition, one can ascertain an understanding of data presented by embodiments of the invention with less effort than prior approaches as relationships lying within the data are visually depicted with greater clarity.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:

FIG. 1 is a block diagram of an illustrative system according to an embodiment of the invention;

FIG. 2 is a flowchart depicting actions performed by presentation manager according to an embodiment of the invention;

FIG. 3 is an illustration of a tree according to the prior art;

FIG. 4 is an illustration of a table according to the prior art;

FIG. 5 is an illustration of a tree table according to the prior art;

FIG. 6 is an illustration of a matrix table according to the prior art;

FIG. 7 is an illustration of a matrix tree table presentation structure according to an embodiment of the invention;

FIG. 8 is an illustration of a matrix tree presentation structure according to an embodiment of the invention;

FIG. 9A is an illustration of a first nested dimension tree presentation structure according to an embodiment of the invention;

FIG. 9B is an illustration of a second nested dimension tree presentation structure according to an embodiment of the invention;

FIG. 10A is an illustration of a first nested dimension tree table presentation structure according to an embodiment of the invention;

FIG. 10B is an illustration of a second nested dimension tree table presentation structure according to an embodiment of the invention; and

FIG. 11 is a block diagram that illustrates a computer system upon which an embodiment of the invention may be implemented.

DETAILED DESCRIPTION OF THE INVENTION

Approaches for rendering data on a display are described. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention discussed herein. It will be apparent, however, that the embodiments of the invention discussed herein may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the embodiments of the invention discussed herein.

Architecture Overview

FIG. 1 is a block diagram of an illustrative system 100 according to an embodiment of the invention. System 100 may be used to render data on a display according to embodiments of the invention. In an embodiment, system 100 comprises display manager 110, display device 112, presentation manager 120, storage medium 130, and communications links 140, 142, and 144.

Display manager 110 represents any mechanism capable of causing digital data to be rendered on display device 112. Non-limiting, illustrative examples of display manager 110 include a web browser and a software application. In an embodiment, display manager 110 receives instructions from presentation manager 120 to render data on display device 112.

Display device 112 represents any physical mechanism capable of displaying rendered digital data. Non-limiting, illustrative examples of display device 112 include a computer monitor, a television set, and a physical display window of a wireless device.

Note that while only one display manager 110 and one display device 112 are depicted in FIG. 1, embodiments of the invention may include any number of display managers and any number of display devices. In some embodiments (not depicted in FIG. 1), display manager 110 may cause digital data to be rendered on multiple display devices 112. In other embodiments (not depicted in FIG. 1) presentation manager 120 may instruct multiple display managers 110 to render data on a display device 112.

In an embodiment, presentation manager 120 represents any computerized entity, such as one or more software components, capable of performing the steps of FIG. 2. FIG. 2 is a flowchart depicting actions performed by presentation manager 120 according to an embodiment of the invention. As shown in FIG. 2, in step 210, presentation manager 120 retrieves data from storage medium 130. The user may identify the data that presentation manager 120 is to retrieve in step 210. For example, the user may submit, to presentation manager 120, a request for a particular web page or other visual presentation that includes a presentation structure according to an embodiment of the invention. The request may also identify a data set to display within the presentation structure.

In step 220, presentation manager 120 generates a visual presentation that includes a presentation structure incorporating, at least of portion of, the retrieved data. Non-limiting, illustrative examples of a visual presentation generated by presentation manager 120 include a web page, an electronic document, and a digital image. In step 230, presentation manager 120 instructs display manger 110 to display the generated visual presentation on display device 112.

While presentation manager 120 is depicted in FIG. 1 as a single entity, in some embodiments, presentation manager 120 may be implemented as two or more entities. For example, in an embodiment, presentation manager 120 may be implemented using a web server and an application server. In certain embodiments of the invention, presentation manager 120 may be implemented using Oracle Fusion Middleware family of products, available from Oracle Corporation of Redwood Shores, Calif.

In some embodiments (not depicted in FIG. 1), display manager 110 and presentation manager 120 may be implemented as a single entity. To illustrate such an embodiment, display manager 110 and presentation manager 120 may be implemented as a single entity (denoted the “combined display and presentation manager”) executing on the same machine, such as a hand held wireless device or personal computer. The combined display and presentation manager may retrieve data (either stored locally or from a remote location), generate a visual presentation, and display the generated visual presentation on display device 112.

Storage medium 130 represents any medium for storing, either persistently or non-persistently, digital data. Non-limiting, illustrative examples of storage medium 130 include a file server and a database management system (DBMS). In the embodiment depicted in FIG. 1, storage medium 130 is implemented using a DBMS comprising a database server 132 and a database 134. In an embodiment, the data stored in storage medium 130 may represent any number of physical and tangible objects, e.g., data stored in storage medium 130 may represent data about an organization, a business, or data about any real-world activity.

Communications link 140 may be implemented by any medium or mechanism that provides for the exchange of data between display device 112 and display manger 110. Communications link 142 may be implemented by any medium or mechanism that provides for the exchange of data between display manager 110 and presentation manager 120. Communications link 144 may be implemented by any medium or mechanism that provides for the exchange of data between presentation manager 120 and storage medium 130. Communications link 146 may be implemented by any medium or mechanism that provides for the exchange of data between database server 132 and database 134. Non-limiting, illustrative examples of communications links 140, 142, 144, and 146 include, without limitation, a network such as a Local Area Network (LAN), Wide Area Network (WAN), Ethernet or the Internet, one or more terrestrial, satellite or wireless links, and serial or parallel printer cables.

FIG. 1 is not intended to depict all embodiments of the invention, as some embodiments of the invention may differ in their implementation than system 100 depicted in FIG. 1. Having explained an illustrative system 100 according to an embodiment of the invention, several illustrative presentation structures will now be discussed to promote a better understanding of embodiments of the invention.

Trees

To facilitate understanding of the embodiments of the invention that will be discussed starting with the section entitled “Matrix Tree Table Presentation Structure,” it will be helpful to review other presentation structures. A presentation structure is a structured format for depicting data on a display.

An exemplary presentation structure is a tree. FIG. 3 is an illustration of tree 300 according to the prior art. Tree 300 may be incorporated as part of a visual presentation generated by presentation manager 120 and shown on display device 112. Tree 300 is an acyclic connected graph where each node of tree 300 has a set of zero or more child nodes, and at most one parent node.

Hierarchical data is depicted in the nodes of tree 300. Hierarchical data is data that is organized in a hierarchical structure using parent/child relationships, where each parent can have many children but each child has, at most, one parent. For example, (a) hierarchical data is stored in nodes 310, 312, 314, 316, and 318, and (b) nodes 312, 314, 316, and 318 are child nodes of node 310.

As every node can be traced to a single origin through a unique path, trees may be helpful for organizing or classifying data. To illustrate, it is readily apparent by looking at tree 300 that the data stored in nodes 312, 314, 316, and 318 has a child relationship to the data stored in node 310.

The visual display of tree 300 may be dynamically updated to expand or collapse nodes of tree 300. A control may be incorporated in the display of a tree to allow a user to either “expand” or “collapse” the child nodes of a particular node. To illustrate, if a user selects control 340 as shown in FIG. 3, then the child nodes of node 310 will “collapse,” and will cease to be displayed. Thereafter, if a user selects control 340, then the child nodes of node 310 will “expand,” and will again be displayed. In this way, a user may update to display of a tree to show the particular portion of the tree in which the user is interested.

While trees are useful in depicting hierarchical data, trees have certain limitations with respect to viewing hierarchical data across different dimensions. Once a tree is populated with data, if a viewer wishes to view the hierarchical data across a different dimension, then another database command to retrieve the desired data may need to be executed, so that the tree can be repopulated with the newly retrieved data. Executing multiple database commands in this manner is not desirable, as it increases the computational resources required as well as the time and effort involved in viewing the desired data.

Tables

Another type of presentation structure is the table. FIG. 4 is an illustration of table 400 according to the prior art. Table 400 may be incorporated as part of a visual presentation generated by presentation manager 120 and shown on display device 112. Table 400 is collection of records, where each record comprises adjacent fields of data. Each row of table 400 corresponds to a distinct record of data. The data type associated with each column of table 400 identifies the type of data stored in a record at the position associated with that column.

Tables are useful for displaying relational data. Relational data is data that is organized based on first-order predicate logic. For example, the data stored in tables of a relational database is relational data. However, tables cannot visually depict any hierarchical relationships that may be present between records of the table.

Tree Tables

A tree table is another type of presentation structure. FIG. 5 is an illustration of tree table 500 according to the prior art. Tree tables are similar to tables in that tree tables are a collection of records, where each record comprises adjacent fields of data. However, in a tree table, one of the columns provides a visual depiction of the hierarchical relationship shared between records of the tree table. The visual depiction of the hierarchical relationship shared between records of the tree table may correspond to a tree of nodes. In effect, the appearance of one column of a tree table is that of a tree of nodes, with each node of the tree depicted in a different row of the tree table, thereby providing the viewer with information about the position of each row within a hierarchy represented by the tree of nodes.

To illustrate, manager column 510 of tree table 500 provides a visual depiction of the hierarchical relationship shared between records of tree table 500. As shown in FIG. 5, record 520 is depicted as being at the top of a hierarchical relationship. Records 522, 526, and 532 are child records of record 520, as visually indicated by manager column 510. As another example, records 528 and 530 are child nodes of record 526, as also visually indicated by manager column 510.

Tree tables advantageously enable a viewer to understand how the records of the tree table relate to each other in a hierarchical relationship. A disadvantage of tree tables, however, is that a tree table does not allow a viewer to view the data stored therein across multiple dimensions.

Matrix Tables

A matrix table is another type of presentation structure. FIG. 6 is an illustration of matrix table 600 according to the prior art. A matrix table is a table that includes a series of rows and a series of columns. Each row of the matrix table is associated with a different dimension instance of a first dimension, and each column of the matrix table is associated with a different dimension instance of a second dimension.

A dimension, as used herein, is a set of related items (individually referred to as a dimension instance) pertaining to a particular topic. A dimension may be used to view data stored in a presentation structure from the perspective of the particular topic associated with the dimension. For example, FIG. 6 depicts two dimensions, namely the job dimension 610 and the department dimension 620. A job dimension instance of job dimension 610 is associated with each column of matrix table 600, and a department dimension instance of department dimension 620 is associated with each row of matrix table 600. Examples of job dimension instances include analyst, clerk, manager, president, and salesmen. Examples of department dimension instances include department 10, department 20, and department 30.

Matrix tables are capable of depicting relational data. Matrix tables are useful in viewing aggregated relational data across two dimension instances. For example, matrix table 600 may depict the average monthly salary of a manager in department 10 is $2,450.00. This salary involves two dimension instances, namely the manager job dimension instance and the department 10 dimension instance.

A disadvantage of a matrix table is that a matrix table can only support exactly two dimensions. For example, matrix table 600 supports job dimension 610 and department dimension 620. However, matrix table 600 can support neither a single dimension nor three or more dimensions.

Another disadvantage of a matrix table is that a matrix table cannot depict hierarchical data. Matrix tables are useful in depicting aggregated data across exactly two dimensions, but they do not provide any mechanism for graphically depicting hierarchical relationships between data.

Matrix Tree Table Presentation Structure

Embodiments of the invention provide improved approaches for displaying data that provide numerous advantages over prior approaches. Further, embodiments of the invention operate under a new paradigm that has not previously been utilized, as embodiments of the invention support new presentation structures that present hierarchical data and relational data in a unified manner.

In an embodiment of the invention, the visual presentation generated by presentation manager 120 in step 220 of FIG. 2 includes a presentation structure referred to herein as a matrix tree table presentation structure. FIG. 7 is an illustration of matrix tree table presentation structure 700 according to an embodiment of the invention. Matrix tree table presentation structures depict data across two dimensions. For example, matrix tree table presentation structure 700 includes region dimension 710 and department dimension 712. Region dimension 710 includes several region dimension instances, namely western region dimension instance 720, eastern region dimension instance 722, and northern region dimension instance 724. Similarly, department dimension 712 includes several department dimension instances, namely department 10 dimension instance 730, department 20 dimension instance 732, and department 30 dimension instance 734. Note that the particular dimensions of matrix tree table presentation structure 700 illustrated in FIG. 7 are merely examples of two possible dimensions, as any dimension may be used with a matrix tree table presentation structure. The number of dimension instances for each dimension depicted in FIG. 7 is merely exemplary, as each dimension in matrix tree table presentation structure 700 may have any number of dimension instances.

As shown in FIG. 7, each dimension instance of matrix tree table presentation structure 700 is associated with either a row or a column of matrix tree table presentation structure 700. For example, each region dimension instance of region dimension 710 is associated with a column of matrix tree table presentation structure 700, while each department dimension instance of department dimension 712 is associated with a row of matrix tree table presentation structure 700. The intersection of each column and each row is a cell. For example, the intersection of western region dimension instance 720 and department 10 dimension instance 730 is cell 740.

In an embodiment, a tree table may be displayed in each cell of matrix tree table presentation structure 700. For example, inside cell 740 a tree table is displayed. A tree table comprises a tree of nodes, and each node of the tree table includes a row of data. To illustrate, node 750 of the tree table in cell 740 includes a row of data.

Matrix tree table presentation structure 700 is capable of storing both relational data and hierarchical data, as matrix tree table presentation structure 700 can store (a) relational data in its columns and rows, and (b) hierarchal data in a tree table present in a cell of matrix tree table presentation structure 700.

Advantageously, hierarchical data for a different combination of dimension instances may be viewed simultaneously using matrix tree table presentation structure 700. To illustrate, matrix tree table presentation structure 700 displays hierarchical data in tree tables in cells 740 and 742. While the hierarchical data depicted in cells 740 and 742 are both associated with department 10 dimension instance 730, the hierarchical data displayed in cell 740 is associated with western region dimension instance 720 while the hierarchical data displayed in cell 742 is associated with eastern region dimension instance 722. As matrix tree table presentation structure 700 may display hierarchical data in any cell, hierarchical data associated with many different combinations of dimension instances may be viewed simultaneously. By viewing many different combinations of hierarchical data simultaneously, the user may make meaningful comparisons between the sets of hierarchical data.

In an embodiment, a particular cell of matrix tree table presentation structure 700 may not be depicted with a tree table. For example, if hierarchical data is not associated with the particular combination of dimension instances associated with a particular cell, then the particular cell may be displayed without a tree table therein. Thus, there is no requirement that each cell of matrix tree table presentation structure 700 be depicted with a tree table. To illustrate, cells of matrix tree table presentation structure 700 associated with northern region dimension 710 do not contain a tree table.

In an embodiment, for each tree table depicted in a cell of matrix tree table presentation structure 700, only a top level node for the tree table may be depicted. A control may be incorporated in the display of a tree table depicted in a cell of matrix tree table presentation structure 700 which allows a user to either “expand” or “collapse” the child nodes of a particular node. When a particular portion of a tree table depicted in a cell of matrix tree table presentation structure 700 is expanded, the newly expanded child nodes are rendered in a manner that graphically depicts each of the newly expanded child nodes to be child nodes of their parent node. Alternately, when a particular portion of a tree table depicted in a cell of matrix tree table presentation structure 700 is collapsed, the child nodes of a parent node are ceased to be displayed, leaving only the parent node to be displayed. In this way, a user may update the display of a tree table depicted within a cell of matrix tree table presentation structure 700 to show the particular portion of the tree table in which the user is interested.

In an embodiment, if a first tree table depicted in a first cell of a particular row is expanded, and a second tree table depicted in a second cell of the same row has a different number of nodes currently being depicted in its hierarchy, then matrix tree table presentation structure 700 automatically adjusts the spacing of the cells of matrix tree table presentation structure 700 such that each cell is clearly depicted to be associated with its corresponding dimension instances. For example, if a user causes the tree table depicted in cell 746 to expand, and if the expanded tree table in cell 746 has three levels of nodes in its hierarchy of nodes, whereas each tree table depicted in each other cell for the row associated with the department 20 dimension instance has only one level of nodes currently depicted, then open space or empty rows may be added to those other tree tables to ensure proper alignment of all tree tables within cells in the row associated with department 20 dimension instance 732.

In an embodiment, in step 210 of FIG. 2, presentation manager 120 retrieves all necessary data from data storage 130 such that each tree table depicted in each cell of matrix tree table presentation structure 700 is populated in its entirety, regardless of whether a particular tree table in a cell is expanded or collapsed. In this way, if a user chooses to expand a particular tree table displayed in a cell of matrix tree table presentation structure 700, then there is little to no delay in rendering an updated display to depict a portion of a tree table moving from the “collapsed” position to an “expanded” position, as the data necessary to update the display to reflect the expanded nodes of the tree table has already been retrieved from data storage 130.

However, in other embodiments of the invention, in step 210 of FIG. 2, presentation manager 120 retrieves, from data storage 130, only the data necessary to depict the top level node of each tree table depicted in each cell of matrix tree table presentation structure 700. In such an embodiment, if a user instructs matrix tree table presentation structure 700 to expand a particular tree table, then presentation manager 120 will subsequently retrieve, from storage medium 130, the data necessary to depict the expanded tree table. A user may cause a particular tree table to expand or collapse by selecting a control associated with a row of the tree table. For example, the icon with the appearance of “+” displayed before a row of a tree table indicates that when that icon is selected, child nodes for that row will be displayed. Similarly, the icon with the appearance of “−” displayed before a row of a tree table indicates that when that icon is selected, the child nodes for that row will cease to be displayed. In this embodiment, the icon having the appearance of “+” in front of a tree or tree table node indicates that the data for the child nodes has not yet been retrieved from the storage medium 130; however, matrix tree table presentation structure 700 possesses all the underlying information necessary to retrieve the child data from storage medium 130 when so instructed. In this embodiment, the rational for not retrieving all the data from storage medium 130 necessary to depict all the child nodes is to enhance performance, as a user interested in viewing detailed information about the western region may not care to see detailed information about the eastern region. Consequently, in this example, the time and resources involved in retrieving data necessary to depict child nodes in tables and tree tables in the eastern region may be avoided.

In other embodiments, the user may configure the behavior of matrix tree table presentation structure 700 in its performance of step 210 such that the user may indicate whether, for one or more cells of matrix tree table presentation structure 700, presentation manager 120 retrieves, from data storage 130, data necessary to render all nodes of a tree table displayed therein or just the top level node of the tree table displayed therein.

In an embodiment, any datum depicted in matrix tree table presentation structure 700 may be associated with a link such that when the datum is selected by a user, another visual presentation is displayed that contains additional information about the selected datum. For example, cell 746 displays a tree table with a top level node that has a row of data with the values “Bipin,” “07/02/2001,” and “9000.” In an embodiment, if a user selects one of these three values, then a web page may be displayed which contains additional information about the selected node. In this example, additional information about the employee named “Bipin” may be provided on the new web page. In this way, a user may cause display device 112 to be updated to display additional information about any datum depicted in matrix tree table presentation structure 700.

In an embodiment, data depicted in matrix tree table presentation structure 700 may be edited by a user. For example, a user may select data depicted in matrix tree table presentation structure 700 using mouse, keyboard, or similar input device. The user may then cause the data to be updated in the display of matrix tree table presentation structure 700. In an embodiment, updating the display of data in matrix tree table presentation structure 700 causes display manager 110 to instruct presentation manager 120 to update data stored in storage medium 130 to reflect the updated data displayed in matrix tree table presentation structure 700. To illustrate, a user may select node 750 using a mouse, and thereafter update the display of Barry's salary from 10000 to 12000. In an embodiment, updating the salary in this manner causes display manager 110 to instruct presentation manager 120 to update the data corresponding to Barry's salary stored in storage medium 130 to reflect that is salary is now 12000. In embodiments of the invention, the user may also make additions and deletions to tree tables depicted in matrix tree table presentation structure 700, e.g., a user may add rows to a tree table or delete rows of a tree table depicted in matrix tree table presentation structure 700, and subsequently, those additions or deletions may be reflected in the data stored in storage medium 130. In such an embodiment, updates to data presented by matrix tree table presentation structure 700 may be performed in a convenient and intuitive manner.

Having described matrix tree table presentation structure 700 according to an embodiment of the invention, another presentation structure for displaying data according to an embodiment of the invention will now be discussed.

Matrix Tree Presentation Structure

In an embodiment of the invention, the visual presentation generated by presentation manager 120 in step 220 of FIG. 2 includes a presentation structure referred to herein as a matrix tree presentation structure. FIG. 8 is an illustration of matrix tree presentation structure 800 according to an embodiment of the invention. Matrix tree presentation structure 800 is similar to matrix tree table presentation structure 700, except that in each cell of matrix tree presentation structure 800, a tree of nodes may be depicted instead of a tree table.

Matrix tree presentation structures depict data across two dimensions. For example, matrix tree presentation structure 800 includes region dimension 810 and department dimension 812. Region dimension 810 includes several region dimension instances, namely western region dimension instance 820, eastern region dimension instance 822, and northern region dimension instance 824. Similarly, department dimension 812 includes several department dimension instances, namely department 10 dimension instance 830, department 20 dimension instance 832, and department 30 dimension instance 834. Note that the particular dimensions of matrix tree presentation structure 800 illustrated in FIG. 8 are merely examples of two possible dimensions, as any dimension may be used with a matrix tree presentation structure. The number of dimension instances for each dimension depicted in FIG. 8 is merely exemplary, as each dimension in matrix tree presentation structure 800 may have any number of dimension instances.

As shown in FIG. 8, each dimension instance of matrix tree presentation structure 800 is associated with either a row or a column of matrix tree presentation structure 800. For example, each region dimension instance of region dimension 810 is associated with a column of matrix tree presentation structure 800, while each department dimension instance of department dimension 812 is associated with a row of matrix tree presentation structure 800. The intersection of each column and each row is a cell. For example, the intersection of western region dimension instance 820 and department 10 dimension instance 830 is cell 840.

In an embodiment, a tree may be displayed in each cell of matrix tree presentation structure 800. For example, inside cell 840 is a tree of nodes. Matrix tree presentation structure 800 is capable of storing both relational data and hierarchical data, as matrix tree presentation structure 800 can store (a) relational data in its columns and rows, and (b) hierarchal data in a tree present in a cell of matrix tree presentation structure 800.

Advantageously, hierarchical data for a different combination of dimension instances may be viewed simultaneously using matrix tree presentation structure 800. To illustrate, matrix tree presentation structure 800 displays hierarchical data in cells 840 and 842. While the hierarchical data depicted in cells 840 and 842 are both associated with department 10 dimension instance 830, the hierarchical data displayed in cell 840 is associated with western region dimension instance 720 while the hierarchical data displayed in cell 842 is associated with eastern region dimension instance 822. As matrix tree presentation structure 800 may display hierarchical data in any cell, hierarchical data associated with many different combinations of dimension instances may be viewed simultaneously. By viewing many different combinations of hierarchical data simultaneously, the user may make meaningful comparisons between the sets of hierarchical data.

In an embodiment, a particular cell of matrix tree presentation structure 800 may not be depicted with a tree. For example, if hierarchical data is not associated with the particular combination of dimension instances associated with a particular cell, then the particular cell may be displayed without depicting a tree therein. Thus, there is no requirement that each cell of matrix tree presentation structure 800 be depicted with a tree table. To illustrate, cells of matrix tree presentation structure 800 associated with northern region dimension 810 do not contain a tree.

In an embodiment, for each tree depicted in a cell of matrix tree presentation structure 800, only a top level node for the tree may be depicted. A control may be incorporated in the display of a tree depicted in a cell of matrix tree presentation structure 800 which allows a user to either “expand” or “collapse” the child nodes of a particular node. When a particular portion of a tree depicted in a cell of matrix tree presentation structure 800 is expanded, the newly expanded child nodes are rendered in a manner that graphically depicts each of the newly expanded child nodes to be child nodes of their parent node. When a particular portion of a tree depicted in a cell of matrix tree presentation structure 800 is collapsed, the child nodes of a parent node are ceased to be displayed, leaving only the parent node to be displayed. In this way, a user may update the display of a tree depicted within a cell of matrix tree presentation structure 800 to show the particular portion of the tree in which the user is interested.

In an embodiment, if a first tree depicted in a first cell of a particular row is expanded, and a second tree depicted in a second cell of the same row has a different number of nodes currently being depicted in its hierarchy, then matrix tree presentation structure 800 automatically adjusts the spacing of the cells of matrix tree presentation structure 800 such that each cell is clearly depicted to be associated with its corresponding dimension instances. For example, if a user causes the tree depicted in cell 842 to expand to show three levels of nodes, whereas only the top level node of the tree depicted in cell 840 is currently being shown, then open space or empty rows may be added in the display of matrix tree presentation structure 800 to ensure proper alignment of all trees so that they are clearly depicted with their corresponding dimension instances.

In an embodiment, in step 210 of FIG. 2, presentation manager 120 retrieves all necessary data from data storage 130 such that each tree depicted in each cell of matrix tree presentation structure 800 is populated in its entirety, regardless of whether a particular tree in a cell is expanded or collapsed. In this way, if a user chooses to expand a particular tree displayed in a cell of matrix tree presentation structure 800, then there is little to no delay in rendering an updated display to depict a portion of a tree moving from the “collapsed” position to an “expanded” position, as the data necessary to update the display to reflect the expanded nodes of the tree has already been retrieved from data storage 130. However, in other embodiments of the invention, in step 210 of FIG. 2, presentation manager 120 retrieves, from data storage 130, only the data necessary to depict the top level node of each tree depicted in each cell of matrix tree presentation structure 800. In such an embodiment, if a user instructs matrix tree presentation structure 800 to expand a particular tree, then presentation manager 120 will subsequently retrieve, from storage medium 130, the data necessary to depict the expanded tree. In other embodiments, the user may configure the behavior of matrix tree presentation structure 800 in its performance of step 210 such that the user may indicate whether, for one or more cells of matrix tree presentation structure 800, presentation manager 120 retrieves, from data storage 130, data necessary to render all nodes of a tree, or just the top level node of a tree, for each tree depicted in matrix tree presentation structure 800.

In an embodiment, any datum depicted in matrix tree presentation structure 800 may be associated with a link such that when the datum is selected by a user, another visual presentation is displayed that contains additional information about the selected datum. For example, cell 842 displays a tree with a top level node that has a row of data having the value “Joy.” In an embodiment, if a user selects the value “Joy” in this tree, then a web page may be displayed which contains additional information about the selected node. In this example, additional information about the employee named “Joy” may be provided on the new web page. In this way, a user may cause display device 112 to be updated to display additional information about any datum depicted in matrix tree presentation structure 800.

In an embodiment, data depicted in matrix tree presentation structure 800 may be edited by a user. For example, a user may select data depicted in matrix tree presentation structure 800 using mouse, keyboard, or similar input device. The user may then cause the data to be updated in the display of matrix tree presentation structure 800. In an embodiment, updating the display of data in matrix tree presentation structure 800 causes display manager 110 to instruct presentation manager 120 to update data stored in storage medium 130 to reflect the updated data displayed in matrix tree presentation structure 800. To illustrate, a user may select a node of the tree depicted in cell 842 using a mouse, and thereafter update the display of the information depicted in that node, e.g., a user may change the name of Vince to David. In an embodiment, updating the name depicted in that node in this manner causes display manager 110 to instruct presentation manager 120 to update the data corresponding to that node stored in storage medium 130 to reflect that the data associated with that node is now “David.” In embodiments of the invention, the user may also make additions and deletions to tables depicted in matrix tree presentation structure 800, e.g., a user may add nodes to a tree or delete nodes to a tree depicted in matrix tree presentation structure 800, and subsequently, those additions or deletions may be reflected in the data stored in storage medium 130. In such an embodiment, updates to data presented by matrix tree presentation structure 800 may be performed in a convenient and intuitive manner.

Having described matrix tree presentation structure 800 according to an embodiment of the invention, another presentation structure for displaying data according to an embodiment of the invention will now be discussed.

Nested Dimension Tree Presentation Structure

In an embodiment of the invention, the visual presentation generated by presentation manager 120 in step 220 of FIG. 2 includes a presentation structure referred to herein as a nested dimension tree presentation structure. FIG. 9A is an illustration of nested dimension tree presentation structure 900 according to an embodiment of the invention.

As depicted in FIG. 9A, nested dimension tree presentation structure 900 includes two dimensions, namely region dimension 910 and department dimension 912. Region dimension 910 includes several dimension instances, namely western region dimension instance 920, eastern region dimension instance 922, and northern region dimension instance 924. Department dimension 912 includes several dimension instances as well, namely department 10 dimension instance 930, department 20 dimension instance 932, and department 30 dimension instance 934. The position of each dimension instance in nested dimension tree presentation structure 900 is aligned under the name of the dimension of which it belongs. The number of dimension instances for each dimension depicted in FIG. 9A is merely exemplary, as each dimension in nested dimension tree presentation structure 900 may have any number of dimension instances.

Nested dimension tree presentation structure 900 depicts region dimension 910 and department dimension 912 in a “nested” manner. That is to say, the dimensions of nested dimension tree presentation structure 900 share a sequential relationship, wherein each dimension in the sequence has a position ranging from the highest position to the lowest position. As shown in FIG. 9A, region dimension 910 has the highest position in the sequence, and department dimension 912 has the lowest position in the sequence. The sequential relationship of the dimensions are graphically portrayed similar to the layers of an onion, with the higher positioned dimensions closer to the exterior (i.e., further way from where the trees of hierarchal data are depicted), and the lower positioned dimensions closer to the interior (i.e., closer to where the trees of hierarchal data are depicted).

In an embodiment, the sequential relationship of the dimensions impacts the alignment of the dimensions and dimension instances in nested dimension tree presentation structure 900. For example, the lower a dimension's position (and by extension their dimension instances positions) is in the sequential relationship of the dimensions, the further the indentation of the dimension (and by extension their dimension instances) will be in nested dimension tree presentation structure 900.

Advantageously, nested dimension tree presentation structure 900 may be configured to display data using any number (zero or more) of dimensions. The number of dimensions incorporated as part of nested dimension tree presentation structure 900 may be configured by a user. A user may submit, to presentation manger 120, user input that identifies (a) how many dimensions to include as part of nested dimension tree presentation structure 900 and (b) what dimensions, including their corresponding dimensional instances, should be included as part of nested dimension tree presentation structure 900.

To illustrate, FIG. 9B is an illustration of nested dimension tree presentation structure 980 according to an embodiment of the invention. Nested dimension tree presentation structure 980 uses three dimensions, namely country dimension 990, region dimension 992, and department dimension 994. As shown in FIG. 9B, each dimension and their corresponding dimension instances are positioned according to their relative position in the sequential relationship between dimensions, as country dimension 990 is the highest positioned dimension and department dimension 994 is the lowest positioned dimension.

If there is any hierarchical data associated with a particular dimensional instance of the lowest positioned dimension, then a tree depicting the associated hierarchical data is shown in association with the particular dimensional instance. For example, in the embodiment depicted in FIG. 9A, there is hierarchical data associated with department 10 dimension instance 930 for the western region dimension instance 920; accordingly, tree 940 is depicted in nested dimension tree presentation structure 900 in association with that occurrence of department 10 dimension instance 930.

In an embodiment of the invention, if there is no hierarchical data associated with a particular dimensional instance of the lowest positioned dimension in the sequence of dimensions, then a tree is not shown in association with the particular dimensional instance. In an embodiment, if there is no hierarchical data associated with a particular dimensional instance of the lowest positioned dimension, then in addition to not depicting a tree with that particular dimension instance, the particular dimension instance itself is also not depicted in the nested dimension tree presentation structure. For example, in the embodiment depicted in FIG. 9B, there is no hierarchical data associated with department 20 dimension instance for the western region dimension instance for the England country dimension instance; accordingly, neither a tree nor an occurrence of department 20 dimension instance for the western region dimension instance for the England country dimension instance is depicted in nested dimension tree presentation structure 980.

In an embodiment of the invention, if, for a particular dimension instance of a dimension which is not the lowest, there is no hierarchical data associated with any lower dimensional instances for that particular dimension instance, then that particular dimension instance itself is not shown in the nested dimension tree presentation structure. For example, in the embodiment depicted in FIG. 9B, there is no hierarchical data associated with any department dimension instance for the northern region dimension instance for the United States country dimension instance; accordingly, the northern region dimension instance for the United States country dimension instance is not depicted in nested dimension tree presentation structure 980.

The visual display of a tree depicted in nested dimension tree presentation structure 900 may be dynamically updated to expand or collapse nodes of the tree. A control may be incorporated in the display of a tree to allow a user to either “expand” or “collapse” the child nodes of a particular node. To illustrate, if a user selects control 960 as shown in FIG. 9A, then the child nodes of node 950 will “expand,” and the child nodes of node 950 will be displayed. Thereafter, if a user selects control 960, then the child nodes of node 950 will “collapse” and the child nodes of node 950 will cease to be displayed. In this way, a user may update to display of a tree in nested dimension tree presentation structure 900 to show the particular portion of the tree in which the user is interested.

In an embodiment, in step 210 of FIG. 2, presentation manager 120 retrieves all necessary data from data storage 130 such that each tree depicted in nested dimension tree presentation structure 900 is populated in its entirety, regardless of whether a particular tree in initially depicted as being expanded or collapsed. In this way, if a user chooses to expand a particular tree displayed in nested dimension tree presentation structure 900, then there is little to no delay in rendering an updated display to depict the portion of a tree moving from the “collapsed” position to an “expanded” position, as the data necessary to update the display to reflect the expanded nodes of the tree has already been retrieved from data storage 130. However, in other embodiments of the invention, in step 210 of FIG. 2, presentation manager 120 retrieves, from data storage 130, only the data necessary to depict the top level node of each tree depicted in nested dimension tree presentation structure 900. In such an embodiment, if a user instructs nested dimension tree presentation structure 900to expand a particular tree, then presentation manager 120 will subsequently retrieve, from storage medium 130, the data necessary to depict the expanded tree. In other embodiments, the user may configure the behavior of nested dimension tree presentation structure 900 in its performance of step 210 such that the user may indicate whether, for each tree depicted in nested dimension tree presentation structure 900, presentation manager 120 retrieves, from data storage 130, data necessary to render all nodes of the tree or just the top level node of the tree.

In an embodiment, any datum depicted in nested dimension tree presentation structure 900 may be associated with a link such that when the datum is selected by a user, another visual presentation is displayed that contains additional information about the selected datum. For example, the top level node of tree 952, as displayed in FIG. 9A, has the value “Greg.” In an embodiment, if a user selects the value “Greg” in this tree, then a web page may be displayed which contains additional information about the selected node. In this example, additional information about the employee named “Greg” may be provided on the new web page. In this way, a user may cause display device 112 to be updated to display additional information about any datum depicted in nested dimension tree presentation structure 900.

Embodiments of the invention employing nested dimension tree presentation structure 900 advantageously enable a user to view multiple sets of hierarchical data in nested dimension tree presentation structure 900. Further, the multiple sets of hierarchical data may be organized based on a configurable number of dimensions, which may include a plurality of two or more, a single dimension, or no dimensions.

In an embodiment, data depicted in nested dimension tree presentation structure 900 may be edited by a user. For example, a user may select data depicted in nested dimension tree presentation structure 900 using mouse, keyboard, or similar input device. The user may then cause the data to be updated in the display of nested dimension tree presentation structure 900. In an embodiment, updating the display of data in nested dimension tree presentation structure 900 causes display manager 110 to instruct presentation manager 120 to update data stored in storage medium 130 to reflect the updated data displayed in nested dimension tree presentation structure 900. To illustrate, a user may select node 944 using a mouse, and thereafter update the display of the name associated with node 944 from “Al” to “Allen.” In an embodiment, updating the name in this manner causes display manager 110 to instruct presentation manager 120 to update the data corresponding to the data associated with node 944 stored in storage medium 130 to reflect that the name has been updated to “Allen.” In embodiments of the invention, the user may also make additions and deletions to trees or dimensions depicted in nested dimension tree presentation structure 900, e.g., a user may (a) add nodes to a tree or delete nodes of a tree depicted in nested dimension tree presentation structure 900 or (b) add or delete a dimension depicted in nested dimension tree presentation structure 900, and subsequently, those additions or deletions may be reflected in the data stored in storage medium 130. In such an embodiment, updates to data presented by nested dimension tree presentation structure 900 may be performed in a convenient and intuitive manner.

Having described nested dimension tree presentation structure 900 according to an embodiment of the invention, another presentation structure for displaying data according to an embodiment of the invention will now be discussed.

Nested Dimension Tree Table Presentation Structure

In an embodiment of the invention, the visual presentation generated by presentation manager 120 in step 220 of FIG. 2 includes a presentation structure referred to herein as a nested dimension tree table presentation structure. FIG. 10A is an illustration of nested dimension tree table presentation structure 1000 according to an embodiment of the invention. Nested dimension tree table presentation structure 1000 is similar to nested dimension tree presentation structure 900, except that a tree table is depicted in nested dimension tree table presentation structure 1000 where a tree of nodes would be depicted in nested dimension tree presentation structure 900.

As depicted in FIG. 10A, nested dimension tree table presentation structure 1000 includes two dimensions, namely region dimension 1010 and department dimension 1012. Region dimension 1010 includes several dimension instances, namely western region dimension instance 1020, eastern region dimension instance 1022, and northern region dimension instance 1024. Department dimension 1012 includes several dimension instances as well, namely department 10 dimension instance 1030, department 20 dimension instance 1032, and department 30 dimension instance 1034. The position of each dimension instance in nested dimension tree table presentation structure 1000 is aligned under the name of the dimension of which it belongs. The number of dimension instances for each dimension depicted in FIG. 10A is merely exemplary, as each dimension in nested dimension tree table presentation structure 1000 may have any number of dimension instances.

Nested dimension tree table presentation structure 1000 depicts region dimension 1010 and department dimension 1012 in a “nested” manner. That is to say, the dimensions of nested dimension tree table presentation structure 1000 share a sequential relationship, wherein each dimension in the sequence has a position ranging from the highest position to the lowest position. As shown in FIG. 10A, region dimension 1010 has the highest position in the sequence, and department dimension 1012 has the lowest position in the sequence. The sequential relationship of the dimensions are graphically portrayed similar to the layers of an onion, with the higher positioned dimensions closer to the exterior (i.e., further way from where the tree tables of hierarchal data are depicted), and the lower positioned dimensions closer to the interior (i.e., closer to where the tree tables of hierarchal data are depicted).

In an embodiment, the sequential relationship of the dimensions impacts the alignment of the dimensions and dimension instances in nested dimension tree table presentation structure 1000. For example, the lower a dimension's position (and by extension their dimension instances positions) is in the sequential relationship of the dimensions, the further the indentation of the dimension (and by extension their dimension instances) will be in nested dimension tree table presentation structure 1000.

Advantageously, nested dimension tree table presentation structure 1000 may be configured to display data using any number (zero or more) of dimensions. The number of dimensions incorporated as part of nested dimension tree table presentation structure 1000 may be configured by a user. A user may submit, to presentation manger 120, user input that identifies (a) how many dimensions to include as part of nested dimension tree table presentation structure 1000 and (b) what dimensions, including their corresponding dimensional instances, should be included as part of nested dimension tree table presentation structure 1000.

To illustrate, FIG. 10B is an illustration of nested dimension tree table presentation structure 1080 according to an embodiment of the invention. Nested dimension tree table presentation structure 1080 uses three dimensions, namely country dimension 1090, region dimension 1092, and department dimension 1094. As shown in FIG. 10B, each dimension and their corresponding dimension instances are positioned according to their relative position in the sequential relationship between dimensions, as country dimension 1090 is the highest positioned dimension and department dimension 1094 is the lowest positioned dimension.

If there is any hierarchical data associated with a particular dimensional instance of the lowest positioned dimension, then a tree table depicting the associated hierarchical data is shown in association with the particular dimensional instance. For example, in the embodiment depicted in FIG. 10A, there is hierarchical data associated with department 10 dimension instance 1030 for the western region dimension instance 1020; accordingly, tree table 1040 is depicted in nested dimension tree table presentation structure 1000 in association with that occurrence of department 10 dimension instance 1030.

In an embodiment of the invention, if there is no hierarchical data associated with a particular dimensional instance of the lowest positioned dimension, then a tree table is not shown in association with the particular dimensional instance. In an embodiment, if there is no hierarchical data associated with a particular dimensional instance of the lowest positioned dimension, then in addition to not depicting a tree table with that particular dimension instance, the particular dimension instance itself is also not depicted in the nested dimension tree table presentation structure. For example, in the embodiment depicted in FIG. 10B, there is no hierarchical data associated with department 20 dimension instance for the western region dimension instance for the England country dimension instance; accordingly, neither a tree table nor an occurrence of department 20 dimension instance for the western region dimension instance for the England country dimension instance is depicted in nested dimension tree table presentation structure 1080.

In an embodiment of the invention, if, for a particular dimension instance of a dimension which is not the lowest, there is no hierarchical data associated with any lower dimensional instances for that particular dimension instance, then that particular dimension instance itself is not shown in the nested dimension tree table presentation structure. For example, in the embodiment depicted in FIG. 10B, there is no hierarchical data associated with any department dimension instance for the northern region dimension instance for the United States country dimension instance; accordingly, the northern region dimension instance for the United States country dimension instance is not depicted in nested dimension tree presentation structure 980.

The visual display of a tree table depicted in nested dimension tree table presentation structure 1000 may be dynamically updated to expand or collapse nodes of the tree depicted within one of the columns of the tree table. A control may be incorporated in the display of a tree depicted within one of the columns of the tree table that allows a user to either “expand” or “collapse” the child nodes of a particular node. To illustrate, if a user selects control 1060 as shown in FIG. 10A, then the child nodes of node 1050 will “expand,” and the child nodes of node 1050 will be displayed. Thereafter, if a user selects control 1060, then the child nodes of node 1050 will “collapse” and the child nodes will cease to be displayed. In this way, a user may update to display of a tree table in nested dimension tree table presentation structure 1000 to show the particular portion of the tree in which the user is interested.

In an embodiment, in step 210 of FIG. 2, presentation manager 120 retrieves all necessary data from data storage 130 such that each tree table depicted in nested dimension tree table presentation structure 1000 is populated in its entirety, regardless of whether a particular tree table is expanded or collapsed. In this way, if a user chooses to expand a particular tree table displayed in nested dimension tree table presentation structure 1000, then there is little to no delay in rendering an updated display to depict a portion of a tree table moving from the “collapsed” position to an “expanded” position, as the data necessary to update the display to reflect the expanded nodes of the tree table has already been retrieved from data storage 130. However, in other embodiments of the invention, in step 210 of FIG. 2, presentation manager 120 retrieves, from data storage 130, only the data necessary to depict the top level node of each tree table depicted in nested dimension tree table presentation structure 1000. In such an embodiment, if a user instructs nested dimension tree table presentation structure 1000 to expand a particular tree table, then presentation manager 120 will subsequently retrieve, from storage medium 130, the data necessary to depict the expanded tree table. In other embodiments, the user may configure the behavior of nested dimension tree table presentation structure 1000 in its performance of step 210 such that the user may indicate whether, for one or more tree tables of nested dimension tree table presentation structure 1000, presentation manager 120 retrieves, from data storage 130, data necessary to render all nodes of the tree table or just the top level node of the tree table.

In an embodiment, any datum depicted in nested dimension tree table presentation structure 1000 may be associated with a link such that when the datum is selected by a user, another visual presentation is displayed that contains additional information about the selected datum. For example, the top level node of tree table 1040, as displayed in FIG. 10A, has the values “Barry,” “01/01/1990,” and “10000.” In an embodiment, if a user selects any of these values, then a web page may be displayed which contains additional information about the selected node. In this example, additional information about the employee named “Barry” may be provided on the new web page. In this way, a user may cause display device 112 to be updated to display additional information about any datum depicted in nested dimension tree table presentation structure 1000.

In an embodiment, data depicted in nested dimension tree table presentation structure 1000 may be edited by a user. For example, a user may select data in nested dimension tree table presentation structure 1000 using mouse, keyboard, or similar input device. The user may then cause the data to be updated in the display of nested dimension tree table presentation structure 1000. In an embodiment, updating the display of data in nested dimension tree table presentation structure 1000 causes display manager 110 to instruct presentation manager 120 to update data stored in storage medium 130 to reflect the updated data displayed in nested dimension tree table presentation structure 1000. To illustrate, a user may select node 1050 using a mouse, and thereafter update the display of Sanej's salary from 7000 to 10000. In an embodiment, updating the salary in this manner causes display manager 110 to instruct presentation manager 120 to update the data corresponding to Sanej's salary stored in storage medium 130 to reflect that is salary is now 10000. In embodiments of the invention, the user may also make additions and deletions to tree tables depicted in dimension tree table presentation structure 1000, e.g., a user may either (a) add rows to a tree table or delete rows of a tree table depicted in dimension tree table presentation structure 1000 or (b) add or delete dimensions depicted in dimension tree table presentation structure 1000, and subsequently, those additions or deletions may be reflected in the data stored in storage medium 130. In such an embodiment, updates to data presented by dimension tree table presentation structure 1000 may be performed in a convenient and intuitive manner.

Embodiments of the invention employing nested dimension tree table presentation structure 1000 advantageously enable a user to view multiple sets of hierarchical data in nested dimension tree table presentation structure 1000. Further, the multiple sets of hierarchical data may be organized based on a configurable number of dimensions, which may include a plurality of two or more, a single dimension, or no dimensions.

Implementing Mechanisms

Presentation structures, such as matrix tree table presentation structure 700, matrix tree presentation structure 800, nested dimension tree presentation structures 900 and 980, and nested dimension tree table presentation structures 1000 and 1080, may each be implemented using a variety of types of technology. To illustrate, non-limiting, illustrative examples of technologies that may be used to implement a presentation structure include HTML, DHTML, Java, JSP, JavaScript, or any combination thereof. The particular type of technology used to implement the presentation structure typically depends upon the context in which it is deployed.

In an embodiment, one or more of display manager 110, presentation manager 120 and storage medium 130 may each be implemented using a computer system. FIG. 11 is a block diagram that illustrates a computer system 1100 upon which an embodiment of the invention may be implemented. In an embodiment, computer system 1100 includes processor 1104, main memory 1106, ROM 1108, storage device 1110, and communication interface 11518. Computer system 1100 includes at least one processor 1104 for processing information. Computer system 1100 also includes a main memory 1106, such as a random access memory (RAM) or other dynamic storage device, for storing information and instructions to be executed by processor 1104. Main memory 1106 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 1104. Computer system 1100 further includes a read only memory (ROM) 1108 or other static storage device for storing static information and instructions for processor 1104. A storage device 1110, such as a magnetic disk or optical disk, is provided for storing information and instructions.

Computer system 1100 may be coupled to a display 1112, such as a cathode ray tube (CRT), a LCD monitor, and a television set, for displaying information to a user. An input device 1114, including alphanumeric and other keys, is coupled to computer system 1100 for communicating information and command selections to processor 1104. Other non-limiting, illustrative examples of input device 1114 include a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 1104 and for controlling cursor movement on display 1112. While only one input device 1114 is depicted in FIG. 11, embodiments of the invention may include any number of input devices 1114 coupled to computer system 1100.

Embodiments of the invention are related to the use of computer system 1100 for implementing the techniques described herein. According to one embodiment of the invention, those techniques are performed by computer system 1100 in response to processor 1104 executing one or more sequences of one or more instructions contained in main memory 1106. Such instructions may be read into main memory 1106 from another machine-readable medium, such as storage device 1110. Execution of the sequences of instructions contained in main memory 1106 causes processor 1104 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement embodiments of the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.

The term “machine-readable storage medium” as used herein refers to any medium that participates in storing instructions which may be provided to processor 1104 for execution. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 1110. Volatile media includes dynamic memory, such as main memory 1106.

Non-limiting, illustrative examples of machine-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer can read.

Various forms of machine readable media may be involved in carrying one or more sequences of one or more instructions to processor 1104 for execution. For example, the instructions may initially be carried on a magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a network link 1120 to computer system 1100.

Communication interface 1118 provides a two-way data communication coupling to a network link 1120 that is connected to a local network. For example, communication interface 1118 may be an integrated services digital network (ISDN) card or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 1118 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, communication interface 1118 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

Network link 1120 typically provides data communication through one or more networks to other data devices. For example, network link 1120 may provide a connection through a local network to a host computer or to data equipment operated by an Internet Service Provider (ISP).

Computer system 1100 can send messages and receive data, including program code, through the network(s), network link 1120 and communication interface 1118. For example, a server might transmit a requested code for an application program through the Internet, a local ISP, a local network, subsequently to communication interface 1118. The received code may be executed by processor 1104 as it is received, and/or stored in storage device 1110, or other non-volatile storage for later execution.

In the foregoing specification, embodiments of the invention have been described with reference to numerous specific details that may vary from implementation to implementation. Thus, the sole and exclusive indicator of what is the invention, and is intended by the applicants to be the invention, is the set of claims that issue from this application, in the specific form in which such claims issue, including any subsequent correction. Any definitions expressly set forth herein for terms contained in such claims shall govern the meaning of such terms as used in the claims. Hence, no limitation, element, property, feature, advantage or attribute that is not expressly recited in a claim should limit the scope of such claim in any way. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. 

1. A method for rendering data on a display, comprising: rendering a matrix table on said display, wherein said matrix table comprises a set of columns and a set of rows, wherein each column in said set of columns contains data pertaining to a different instance of a first dimension, wherein each row in said set of rows contains data pertaining to a different instance of a second dimension, wherein the first dimension is different than said second dimension, and wherein the intersection of each column, of said set of columns, with each row, of said set of rows, is a cell; and rendering, within at least one cell of said matrix table, a tree table, wherein said tree table comprises a tree of nodes, and wherein each node of said tree of nodes comprises a row of data.
 2. The method of claim 1, wherein said tree of nodes includes at least a top level node and one or more child nodes of said top level node, and wherein only said top level node of said tree of nodes is rendered on said display.
 3. The method of claim 1, wherein said tree of nodes includes at least a top level node and one or more child nodes of said top level node, and wherein only said top level node of said tree of nodes is initially rendered on said display, and wherein the method further comprises: in response to receiving user input, causing said one or more child nodes of said top level node to be rendered on said display in a manner that graphically depicts each of said one or more child nodes to be child nodes of said top level node.
 4. The method of claim 1, wherein said tree of nodes includes at least a top level node and one or more child nodes of said top level node, and wherein only said top level node of said tree of nodes is initially rendered on said display, and wherein the method further comprises: in response to receiving user input that selects said top level node, performing the steps of: retrieving child data corresponding to said one or more child nodes of said top level node, wherein said retrieving said child data is not performed until after said user input is received, and updating said display to render said one or more child nodes on said display using said child data.
 5. The method of claim 1, wherein said data rendered on said display includes both hierarchical data and relational data, wherein said hierarchical data is rendered in said tree of nodes, and wherein said relational data is rendered in said matrix table.
 6. The method of claim 1, wherein one or more cells of said matrix table do not contain a tree table.
 7. The method of claim 1, wherein a particular node of said tree of nodes contains a link to a web page that contains additional information about said particular node.
 8. A method for rendering data on a display, comprising: rendering a matrix table on said display, wherein said matrix table comprises a set of columns and a set of rows, wherein each column in said set of columns contains data pertaining to a different instance of a first dimension, wherein each row in said set of rows contains data pertaining to a different instance of a second dimension, wherein said first dimension is different than said second dimension, and wherein the intersection of each column of said matrix table with each row of said matrix table is a cell; rendering, within a first cell of said matrix table, a first tree of nodes; and rendering, within a different cell of said matrix table than said first cell, a second tree of nodes, wherein said first tree of nodes displays hierarchical data for a first pair of instances of dimensions, wherein said second tree of nodes displays hierarchical data for a second pair of instances of dimensions, and wherein said first pair of instances of dimensions is different than said second pair of instances of dimensions.
 9. The method of claim 8, wherein said first tree of nodes includes a top level node and one or more child nodes of said top level node, and wherein only said top level node of said first tree of nodes is rendered on said display.
 10. The method of claim 8, wherein said first tree of nodes includes at least a top level node and one or more child nodes of said top level node, and wherein only said top level node of said first tree of nodes is initially rendered on said display, and wherein the method further comprises: in response to receiving user input, causing said one or more child nodes of said top level node to be rendered on said display in a manner that graphically depicts each of said one or more child nodes to be child nodes of said top level node.
 11. The method of claim 8, wherein said first tree of nodes includes at least a top level node and one or more child nodes of said top level node, and wherein only said top level node of said first tree of nodes is initially rendered on said display, and wherein the method further comprises: in response to receiving user input that selects said top level node, performing the steps of: retrieving child data corresponding to said one or more child nodes of said top level node, wherein said retrieving said child data is not performed until said user input is received, and updating said display to render said one or more child nodes on said display using said child data.
 12. The method of claim 8, wherein said data rendered on said display includes both hierarchical data and relational data, wherein said hierarchical data is rendered in said first tree of nodes and said second tree of nodes, and wherein said relational data is rendered in said matrix table.
 13. The method of claim 8, wherein one or more cells of said matrix table do not contain a tree of nodes.
 14. A machine-readable storage medium storing one or more sequences of instructions for rendering data on a display, which when executed, cause: rendering a matrix table on said display, wherein said matrix table comprises a set of columns and a set of rows, wherein each column in said set of columns contains data pertaining to an instance of a first dimension, wherein each row in said set of rows contains data pertaining to an instance of a different dimension than said first dimension, and wherein the intersection of each column, of said set of columns, with each row, of said set of rows, is a cell; and rendering, within at least one cell of said matrix table, a tree table, wherein said tree table comprises a tree of nodes, and wherein each node of said tree of nodes comprises a row of data.
 15. The machine-readable storage medium of claim 14, wherein said tree of nodes includes at least a top level node and one or more child nodes of said top level node, and wherein only said top level node of said tree of nodes is rendered on said display.
 16. The machine-readable storage medium of claim 14, wherein said tree of nodes includes at least a top level node and one or more child nodes of said top level node, and wherein only said top level node of said tree of nodes is initially rendered on said display, and wherein execution of said one or more sequences of instructions further causes: in response to receiving user input, causing said one or more child nodes of said top level node to be rendered on said display in a manner that graphically depicts each of said one or more child nodes to be child nodes of said top level node.
 17. The machine-readable storage medium of claim 14, wherein said tree of nodes includes at least a top level node and one or more child nodes of said top level node, and wherein only said top level node of said tree of nodes is initially rendered on said display, and wherein execution of said one or more sequences of instructions further causes: in response to receiving user input that selects said top level node, performing the steps of: retrieving child data corresponding to said one or more child nodes of said top level node, wherein said retrieving said child data is not performed until after said user input is received, and updating said display to render said one or more child nodes on said display using said child data.
 18. The machine-readable storage medium of claim 14, wherein said data rendered on said display includes both hierarchical data and relational data, wherein said hierarchical data is rendered in said tree of nodes, and wherein said relational data is rendered in said matrix table.
 19. The machine-readable storage medium of claim 14, wherein one or more cells of said matrix table do not contain a tree table.
 20. The machine-readable storage medium of claim 14, wherein a particular node of said tree of nodes contains a link to a web page that contains additional information about said particular node.
 21. A machine-readable storage medium storing one or more sequences of instructions for rendering data on a display, which when executed, cause: rendering a matrix table on said display, wherein said matrix table comprises a set of columns and a set of rows, wherein each column in said set of columns contains data pertaining to an instance of a first dimension, wherein each row in said set of rows contains data pertaining to an instance of a different dimension than said first dimension, and wherein the intersection of each column of said matrix table with each row of said matrix table is a cell; rendering, within a first cell of said matrix table, a first tree of nodes; and rendering, within a different cell of said matrix table than said first cell, a second tree of nodes, wherein said first tree of nodes displays hierarchical data for a first pair of instances of dimensions, wherein said second tree of nodes displays hierarchical data for a second pair of instances of dimensions, and wherein said first pair of instances of dimensions is different than said second pair of instances of dimensions.
 22. The machine-readable storage medium of claim 21, wherein said first tree of nodes includes a top level node and one or more child nodes of said top level node, and wherein only said top level node of said first tree of nodes is rendered on said display.
 23. The machine-readable storage medium of claim 21, wherein said first tree of nodes includes at least a top level node and one or more child nodes of said top level node, and wherein only said top level node of said first tree of nodes is initially rendered on said display, and wherein execution of said one or more sequences of instructions further causes: in response to receiving user input, causing said one or more child nodes of said top level node to be rendered on said display in a manner that graphically depicts each of said one or more child nodes to be child nodes of said top level node.
 24. The machine-readable storage medium of claim 21, wherein said first tree of nodes includes at least a top level node and one or more child nodes of said top level node, and wherein only said top level node of said first tree of nodes is initially rendered on said display, and wherein execution of said one or more sequences of instructions further causes: in response to receiving user input that selects said top level node, performing the steps of: retrieving child data corresponding to said one or more child nodes of said top level node, wherein said retrieving said child data is not performed until said user input is received, and updating said display to render said one or more child nodes on said display using said child data.
 25. The machine-readable storage medium of claim 21, wherein said data rendered on said display includes both hierarchical data and relational data, wherein said hierarchical data is rendered in said first tree of nodes and said second tree of nodes, and wherein said relational data is rendered in said matrix table. 